Welcome Guest, you are in: Login
CTS Futures

Page History: Sequence Reset

Compare Page Revisions



« Older Revision - Back to Page History - Newer Revision »


Page Revision: 2012/09/06 09:24


Resetting Sequence Numbers

With the Resend Request message, a receiving application asks for the retransmission of previously sent messages. The previously sent messages span over an input range of sequence numbers. The input range is specified with BeginSeqNo (Tag 7) and EndSeqNo (Tag 16). To request only one message, BeginSeqNo is set equal to EndSeqNo. The specification of zero (0) for EndSeqNo indicates that the requested range would end with the sent message of highest sequence number (i.e. the last message sent).

Resend Request messages are commonly encountered in the following conditions:

  1. Sequence number gap is detected
  2. A message has been lost by a receiving application
  3. Part of re-initialization process for an out-of sequence condition

A proper response for a Resend Request includes all the application messages but no administrative message (with the exception of the Session Reject - Tag 35=9). The resending application may decide not to resend specific messages (e.g. NewOrder) if it considers it risky or the messages would be resent out of an acceptable time window. All messages resent by the application honoring the Resend Request must be labeled as a Possible Duplicate (i.e. Tag 43=Y). The T4 FIX API will honor all Possible Duplicates received. If messages gaps exists in the resent message lot, Sequence Reset messages can be received to fill the sequence number gap. This is a common occurance when administrative messages are excluded from the resent lot.

Message Dictionary

TagField NameReq'dComments
Standard HeaderYMsgType = 4
123GapFillFlagYIndicates that the Sequence Reset message is replacing administrative or application messages which will not be resent.
36NewSeqNo|| YNew sequence number
Standard TrailerY

Sample Message


Resetting Sequence Number to 30

34=2|49=test|56=T4Test|50=TraderName|52=20120906-14:14:16.424|36=30|123=Y|
[FIXSEQUENCERESET]
[MsgSeqNum] 34 = 2
[SenderCompID] 49 = test
[TargetCompID] 56 = T4Test
[SenderSubID] 50 = TraderName
[SendingTime] 52 = 20120906-14:14:16.424
[NewSeqNo] 36 = 30
[GapFillFlag] 123 = Y (YES)


FIX API Home Page.

Trade how you want, where you want

support@ctsfutures.com (312) 939 0164

2 Pierce Pl, Suite 200, Itasca, IL 60143

© 2009-2023 Cunningham Trading Systems LLC All rights reserved.